Skip to content
This repository was archived by the owner on Sep 8, 2025. It is now read-only.

Conversation

isaacelee
Copy link

@isaacelee isaacelee commented Oct 26, 2018

I removed the duplicate functions from /fixtures/normalization.py mainly except the
functions under the header "Fixture Normalizers" as I felt those belonged and as
such removed them from /_utils/normalization.py instead.
Meant to fix #1407

…nly except the

functions under the header "Fixture Normalizers" as I felt those belonged and as
such removed them from /_utils/normalization.py instead.
@pipermerriam
Copy link
Member

@isaacelee lots of failed tests. Looks like you need to spend some time updating the imports for some of these to import from the right location.

cburgdorf and others added 18 commits October 29, 2018 23:07
These methods were named so that they appeared
private by convention. This convention causes
trouble in the documentation where these methods
are righfully dropped. Since these methods aren't
really private in reality (they need to be overwritten
in subclasses), they were renamed, migrating their
naming from `_*` to `do_*`.
This enables the plugin to read the status of the
four formal states a plugin can be in. Previously
even though the four states existed implicitly,
it could only be differentiated between the
STARTED/STOPPED state based on the `running`
bool.

This change also has the nice benefit that we
can make stronger assumptions about the status
inside `start()` and raise an exception if
`start()` was called on a plugin that isn't in
the correct status to call `start()`
…nly except the

functions under the header "Fixture Normalizers" as I felt those belonged and as
such removed them from /_utils/normalization.py instead.
…nly except the

functions under the header "Fixture Normalizers" as I felt those belonged and as
such removed them from /_utils/normalization.py instead.
@isaacelee
Copy link
Author

Not sure if I've made a complete mess of things trying to update my fork with the master branch, let me know if I need to create a new pull request and I can try and refork and do it right the first time. Hopefully this sorts everything out and sorry about the delay, midterm exams.

@pipermerriam
Copy link
Member

This PR will need to be fixed as it's history isn't something we can merge. I'd recommend going and reading up on how to do a git rebase.

@cburgdorf
Copy link
Contributor

Apart from the PR not getting the rebase it needs, this was fixed in #1486

@cburgdorf cburgdorf closed this Dec 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove duplicate utility functions from eth.tools.fixtures.normalization

5 participants